[pull] master from supabase:master - #1124

## What kind of change does this PR introduce?

Docs consistency fix for the [CLI getting-started
guide](https://supabase.com/docs/guides/local-development/cli/getting-started).

The page has three install-channel tab groups (Installing, Beta channel,
Updating the Supabase CLI). The first two order tabs **npm → macOS →
Windows → Linux** with npm as the default, but the Updating section put
npm last and defaulted to macOS. This PR aligns all three, plus two
related consistency fixes found while auditing the CLI-focused pages:

- Move the npm tab first in the Updating section and set
`defaultActiveId="npm"`, matching the other two groups
- Rename the Updating section's `#### Linux package manager` heading to
`#### Linux packages` to match the Installing and Beta channel sections
(in-page `#linux-packages` links target the first occurrence in
Installing, so they are unaffected)
- Add `queryGroup="platform"` to all three groups so the selected
platform stays in sync across them and persists in the URL — the same
mechanism the page's Access services tabs (`access-method`) and the
local-development overview (`package-manager`) already use

Other CLI-focused pages were checked (`cli/testing-and-linting`,
`cli-workflows`, `guides/cli`, `local-development` overview) and have no
similar tab inconsistencies.

Noticed in passing, intentionally not changed here: the Updating npm tab
suggests `npm update supabase@beta --save-dev` for the beta channel, but
`npm update` doesn't accept a dist-tag — switching to beta should be
`npm install supabase@beta --save-dev`. Left for a follow-up since it's
a content bug, not an ordering issue.

Validation: `pnpm lint:mdx` and Prettier pass with no findings on this
file.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit

* **Documentation**
* Improved the Supabase CLI installation and update guide with clearer
platform-specific tab behavior.
* Refined the “Updating the Supabase CLI” tabs to default to npm, and
added stable/beta npm update instructions in the npm panel.
* Updated Linux update wording and re-formatted the step list under the
Linux packages tab for better readability.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->

Co-authored-by: Claude Fable 5 <noreply@anthropic.com>

)

## Context

Replaces all usage of `form.watch()` to use `useWatch` instead + follows
the "name what you watch" convention as specified in the react-hook-form
skills.

There's also a small refactor in `SmtpForm.tsx` which removes the
unnecessary use of a `useState` to track if SMTP is enabled or not

<!-- This is an auto-generated comment: release notes by coderabbit.ai
-->
## Summary by CodeRabbit

* **Improvements**
* Updated many Studio forms to watch specific fields more precisely,
improving live UI updates for previews, warnings, conditional sections,
and validation messages.
* Enhanced responsiveness across settings, authentication, billing,
storage, integrations, and support flows while keeping save/update
behavior the same.
* **Refined Experiences**
* Improved the analytics table creation flow with tighter, enum-based
column type validation and structured, type-specific column options.
* **Preserved Behavior**
* Maintained existing permission checks, submission flows, and
account-management workflows.
<!-- end of auto-generated comment: release notes by coderabbit.ai -->